|
|
|
|
|
Day 9
Breaking Up an Application into Subsystems |
|
|
|
| |
 |
|
|
|
|
The Subsystem-Based Model of Application Development |
|
|
|
| |
|
|
|
|
|
The Object Structure of a Complete Subsystem |
|
|
|
| |
|
|
|
|
|
The Object Interaction Structure of a Subsystem |
|
|
|
| |
|
|
|
|
|
Encapsulation for Subsystems |
|
|
|
| |
|
|
|
|
|
Identifying and Using Design Patterns |
|
|
|
| |
|
|
|
|
|
Defining the Design Pattern |
|
|
|
| |
|
|
|
|
|
Naming the Design Pattern |
|
|
|
| |
|
|
|
|
|
Applying the Design Pattern |
|
|
|
| |
|
|
|
|
|
Describing the Solution |
|
|
|
| |
|
|
|
|
|
Listing the Consequences |
|
|
|
| |
|
|
|
|
|
How to Use and Reuse Design Patterns for Subsystems |
|
|
|
| |
|
|
|
|
|
Analyzing and Designing Subsystem Interfaces |
|
|
|
| |
|
|
|
|
|
Real-World Case Studies |
|
|
|
| |
|
|
|
|
|
Candidate Subsystems for the Samsona Bank Teller System Example |
|
|
|
| |
|
|
|
|
|
Summary |
|
|
|
| |
|
|
|
|
|
Q&A |
|
|
|
| |
|
|
|
|
|
Workshop |
|
|
|
| |
|
|
|
|
|
Quiz |
|
|
|
| |
|
|
|
|
|
Exercises |
|
|
|
| |
|
|
|
|
|
Day 10
Refining Use Cases as Application and Subsystem Architecture Blueprints |
|
|
|
| |
|
|
|
|
|
Revisiting Use Cases in Your Environment |
|
|
|
| |
|
|
|
|
|
The Problem Statement |
|
|
|
| |
|
|
|
|
|
The Use-Case Model |
|
|
|
| |
|
|
|
|
|
Refining User Requirements into a Better Use-Case Model |
|
|
|
| |
|
|
|
|
|
Working with End Users |
|
|
|
| |
|
|
|
|
|
Working with Business Analysts |
|
|
|
| |
|
|
|
|
|
Working with Executives |
|
|
|
| |
|
|
|
|
|
Working with Project Managers |
|
|
|
| |
|
|
|
|
|
New Discoveries in How the End User Uses the Visual Basic Application |
|
|
|
| |
|
|
|
|
|
Documenting the Expected Response of the System |
|
|
|
| |